-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix regression from lazy opaque types #93783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
6c47458
to
239f1e7
Compare
@bors p=1 rollup=never as this fixes broken perf, but I don't feel comfortable approving this myself right now. |
@bors r+ This is hacky, but I think better to land this and come up with a better fix than to let this hit nightly. |
📌 Commit 239f1e7 has been approved by |
⌛ Testing commit 239f1e7 with merge 97a8e8b5b5eec9a7cc44b553855cfe3c5dfd421e... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
note for t-infra and tracking, the retry was because of #93784 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (cc38176): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
The breakage was found in #92007 (comment) and has not hit nightly yet.